-
Notifications
You must be signed in to change notification settings - Fork 576
fix: supports empty message object #2369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feature/dynamic-messaging #2369 +/- ##
=============================================================
- Coverage 51.82% 51.75% -0.08%
=============================================================
Files 149 149
Lines 12322 12338 +16
Branches 700 703 +3
=============================================================
- Hits 6386 6385 -1
- Misses 5831 5848 +17
Partials 105 105
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@wsbrunson Please review at your convenience, thanks! |
showPoweredBy: boolean, | ||
layout: string, | ||
|}; | ||
export function calculateShowPoweredBy( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
Description
Ensures that an empty message object input (e.g. message: {}) results in a message render by populating message props align, position, and color with computed default values.
Why are we making these changes? Include references to any related Jira tasks or GitHub Issues
Reproduction Steps (if applicable)
Screenshots (if applicable)
Dependent Changes (if applicable)
Groups who should review (if applicable)
❤️ Thank you!